Release 10.1A: OpenEdge Development:
Progress Dynamics Advanced Development

Using the Configuration File Manager

The Configuration File Manager is different in its construction from the other Progress Dynamics managers. Because it starts every other manager in the framework, it is the first procedure run by Progress Dynamics on startup. Its principal procedure file is af/app/afxmlcfgp.p, and it does not use the techniques described in the "Manager architecture" section. Because the Configuration File Manager is so fundamental to the framework, its handle is not stored as a global variable as with the other basic managers. Instead, it makes itself a super procedure of the Progress session it is run in, so that any procedure in an application can run one of its entry points as if it was in the application itself (IN THIS-PROCEDURE, in other words), and it can be found in the session super procedure.

The "Overview of the managers" section summarizes the utilities that you normally use to define and maintain manager types, session types, session properties, and other data in the domain of the Configuration File Manager. More information on using those utilities is in OpenEdge Development: Progress Dynamics Administration . This section notes the API calls in this manager that you are most likely to want to use in your code.